fix: Support Kimi Tokenizer using allow_special_tokens [TL-76] #420
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ajcasagrande
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes to tokenizer functionality:
Added a new
supports_kwargfunction ingenai-perf/genai_perf/utils.pyto determine if a method of an object accepts a specific keyword argument.Updated the
set_tokenizermethod ingenai-perf/genai_perf/tokenizer.pyto use thesupports_kwargutility. If the tokenizer'sencodemethod supports theallow_special_tokensargument, the method dynamically adjusts the call arguments (_call_args,_encode_args,_decode_args) to align with the tokenizer's behavior.